Skip to content

chore(release): tinychannels 0.2.1 - #175

Merged
senamakel merged 3 commits into
mainfrom
release-0.2.1
Nov 12, 2026
Merged

senamakel merged 3 commits into
mainfrom
release-0.2.1

Conversation

@senamakel

@senamakel senamakel commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

Bumps the workspace from 0.2.0 to 0.2.1 so main can be released. OpenHuman needs the release to move to rusqlite 0.41 (RUSTSEC-2026-0459): tinyhumansai/tinywallet's next release, which carries the x402 upto/sign-in work (tinyhumansai/tinywallet#131), uses tinystoragedrivers 2.1.3, and OpenHuman can only take it once every module it builds from source is on rusqlite 0.41.

Why a patch: since v0.2.0, main has only fixes and dependency bumps:

Changes: version in the root [workspace.package], plus the version lines in Cargo.lock, crates/tinychannels-client/test-fixture/Cargo.lock and proofs/storage-needs-consumer/Cargo.lock. No code changes.

Validation: cargo build --locked --workspace passes locally.

After merge: tag v0.2.1 at the merge commit.

Summary by CodeRabbit

  • Chores
    • Updated the workspace package version from 0.2.0 to 0.2.1.
    • No changes to exported or public entities are included in this update. The available change summary does not describe any new features, bug fixes, or changes to application behavior.

senamakel and others added 2 commits November 12, 2026 21:40
Update the shared workspace version from 0.2.0 to 0.2.1 so every crate in the workspace is packaged under the new release number.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
Update the pinned tinychannels-bus version from 0.2.0 to 0.2.1 in the test fixture and storage-needs-consumer proof lockfiles so they match the released crate.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
@tinysweeper

tinysweeper Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Tiny Sweeper review

Reviewed head: eb9bb52283be79aa3496d3154a016e0aeb22a025

Verdict: Ready for maintainer review · Priority: none
Coverage: Reviewed 2 of 5 files; not reviewed: Cargo.lock, crates/tinychann…, and 1 additional unreviewed files.
Pull request purpose (title): chore(release): tiny…

Diagnostics and supporting details

Full summary

Pull request purpose (title): chore(release): tinychannels 0.2.1. Release chore bumping the workspace version from 0.2.0 to 0.2.1 so main can be released, now also adding a tokio unit test for channel control routing. The whole-pull-request evidence reports five changed files: Cargo.lock, Cargo.toml, crates/tinychannels-client/test-fixture/Cargo.lock, crates/tinychannels-module/src/service_tests.rs and proofs/storage-needs-consumer/Cargo.lock. Latest-push-delta evidence is unavailable, so no push-delta claims are made.

Unreviewed paths

  • Cargo.lock
  • crates/tinychannels-client/test-fixture/Cargo.lock
  • proofs/storage-needs-consumer/Cargo.lock

Review snapshot

Change surface Files Review signal Count
Production 0 Active findings 0
Tests 1 Noted findings 0
Documentation 0 Resolved findings 0
Configuration 1 Pending checks/questions 0

Completeness: Complete
Test assessment: No supported feature-to-test mapping was available; this does not mean tests are absent or passed.

What changed

The pull-request title and description state this is a release chore moving the workspace from 0.2.0 to 0.2.1 so main can be released, motivated by the need to move to rusqlite 0.41 for RUSTSEC-2026-0459, described as containing only fixes and dependency bumps since v0.2.0 and with no code changes. The whole-pull-request evidence lists Cargo.lock, Cargo.toml, crates/tinychannels-client/test-fixture/Cargo.lock, crates/tinychannels-module/src/service_tests.rs and proofs/storage-needs-consumer/Cargo.lock with 98 additions and 9 deletions. The reviewed diff shows the workspace version line changing from "0.2.0" to "0.2.1" and adds a new async test function route_commands_cover_listings_unknown_providers_empty_models_and_oversized_requests in crates/tinychannels-module/src/service_tests.rs.

Features

  • Modified — Workspace version bump to 0.2.1: The workspace package version moves from 0.2.0 to 0.2.1, which workspace members inheriting the version take up, supporting the described release of main. (Cargo.toml)

Tests

No supported feature-to-test mapping was produced. Test execution is not inferred.

Findings

No active actionable findings.

Before merge

None.

Agent review details

critique

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: This adds one tokio test covering route control cases (unknown provider, same-provider switch, empty model id, help listings) and the oversized `Overflow` request rejection. The test uses only existing helpers and its assertions match the shapes of `ChannelControlRequest`/`ChannelControlResult`; I found no defect in it. _The code index is behind this pull request (indexed at `63db0659aba3`), so retrieved context may be out of date._

security

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: This adds one module-local unit test in a sibling `_tests.rs` file, using the existing `inbound_preparation_service`/`enable_remote_providers` fixtures. It touches no production code, no network, no secrets, and no permissions; it merely asserts existing command-routing behaviour on fixture input. I found no security or correctness defect introduced by this file. _The code index is behind this pull request (indexed at `63db0659aba3`), so retrieved context may be out of date._

tests

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Lane summary: The added test exercises the routing command surface with concrete expected strings for unknown providers, same-provider switches, empty model IDs, and listings, plus an error path for an oversized request, so it asserts behaviour that would fail if it regressed. The `starts_with`/`is_some_and(!empty)` assertions on the listing are loose, but they are not vacuous — a missing or empty reply fails them — so this is a nit rather than a defect. No new public API, no serialization change, and no reachable input goes uncovered by the diff. _The code index is behind this pull request (indexed at `63db0659aba3`), so retrieved context may be out of date._

commits

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: Commits lane answered reporting no sensitive content in committed files.
  • Lane summary: No sensitive content in committed files. _The code index is behind this pull request (indexed at `63db0659aba3`), so retrieved context may be out of date._

description

  • Conclusion: Success
  • Scope reviewed: all assigned evidence
  • Positive: Description lane answered with no reportable defect: the workspace version bump matches the description and the added test does not contradict the stated scope, with the only discrepancy being lockfile updates the description claims that are not present in the diff.
  • Lane summary: The change under review is the workspace version bump from 0.2.0 to 0.2.1, which matches the PR description exactly, and the added test exercises routing, listing, and oversized-request paths without contradicting the stated scope. No defects found; the only discrepancy is that the diff shown here is the version bump while the description also claims lockfile updates not present in this diff. _The code index is behind this pull request (indexed at `63db0659aba3`), so retrieved context may be out of date._
Evidence and run details
  • Models: ladder/vectors-oai3, deepseek-v4.1-flash
  • Spend: $0.000722
  • Tokens: 136586 input · 2965 output · 34816 cached · 199 embedding
  • Updated: 2026-11-12T22:33:55Z
Head State Pass summary
63db0659aba3 ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-11-12T21:42:30Z)
eb9bb52283be ready for maintainer review 0 active finding(s), 0 resolved finding(s) (at 2026-11-12T22:33:55Z)

tinysweeper 0.1.2

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-12T22:34:35.126375Z eb9bb52 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Explain Change →

Warning

Review limit reached

  • Run on-demand review

This review includes 1 billable file and costs up to $0.25.

Or wait 8 minutes for your next included review.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 35e5c1be-1b7c-49c3-b9c1-4c0006e3fafb
Commits

Reviewing files that changed from the base of the PR and between 63db065 and eb9bb52.

Files selected for processing: 1

  • crates/tinychannels-module/src/service_tests.rs

No actionable comments were generated in the recent review.

Walkthrough

The workspace package version changes from 0.2.0 to 0.2.1.

Changes: Release Version

Layer / File(s) Summary
Package version update
Cargo.toml
The workspace package version changes from 0.2.0 to 0.2.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Possibly related PRs

Suggested reviewers: tinysweeper, m3ga-mind

Merge Risk: Minimal · previous review 63db0

This is a version-only release bump with no behavior change, so merge risk is minimal.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title "chore(release): tinychannels 0.2.1" names the main change: a release version bump of the tinychannels workspace from 0.2.0 to 0.2.1. The raw summary confirms the only tracked change is the …
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title "chore(release): tinychannels 0.2.1" names the main change: a release version bump of the tinychannels workspace from 0.2.0 to 0.2.1. The raw summary confirms the only tracked change is the workspace version in Cargo.toml, and the objectives describe the same release, so the title is specific and accurate.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

A small version takes a hop,
From zero two to one atop.
Cargo marks the change in place,
A rabbit checks the release pace.
One more nibble, neat and done!

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 2a083d87-9d7d-48a4-874c-2613e1dc0830
Commits

Reviewing files that changed from the base of the PR and between 842855b and 63db065.

Files ignored due to path filters: 3

  • Cargo.lock is excluded by !**/*.lock
  • crates/tinychannels-client/test-fixture/Cargo.lock is excluded by !**/*.lock
  • proofs/storage-needs-consumer/Cargo.lock is excluded by !**/*.lock
Files selected for processing: 1

  • Cargo.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@tinysweeper tinysweeper Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tinysweeper found nothing blocking. Approving.

Diagnostics

Total spend: $0.0011

@tinysweeper tinysweeper Bot added the priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect. label Nov 12, 2026
Adds a test exercising provider listings, unknown providers, empty model IDs, and oversized requests through the channel control route path, so these edge cases are verified to return the expected replies and rejections.

Auto-committed-on: cuttlefish
Co-authored-by: Medulla <medulla@tinyhumans.ai>
@senamakel

Copy link
Copy Markdown
Member Author

Merging with --admin past module-ci / coverage. The failure comes from the toolchain, not from this change.

  • main's last green coverage run (842855b, 2026-11-11) used rustc 1.99.1. This PR's runs used rustc 1.100.0 (released 2026-11-09), which the CI toolchain resolver now picks.
  • Under 1.100 the per-file report flags files this PR doesn't touch: approvals/mod.rs, delivery/progressive/*, prepare_connect.rs and others. Main at the same commit would fail the gate the same way.
  • This PR is a version bump (0.2.0 → 0.2.1) plus one added test covering control.rs route edge cases.
  • Every other check passed, and cargo build --locked --workspace and clippy pass locally.

Follow-up: pin the coverage toolchain in the shared workflow, or bring these files back over 90% under 1.100.

@senamakel
senamakel merged commit a1d0cff into main Nov 12, 2026
35 of 37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority: p3 Whenever. Cosmetic, a nicety, or a cleanup with no user visible effect.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant